I have a question for all you hard working people on this forum. Imagine the following scenario: You have one source module containing requirements, the source module contains links to one or more target modules. The source module will be open at all times. You are editing, lets say targetModule1, both source and target module contains an enumeration type attribute called "Status". The source module contains requirements, and the target modules contains proofs of said requirements. What I'm looking for is a way to implement the following functionality: When I change the the "Status" attribute in targetModule1 for proof n. 43 I want the "Status" attribute in the source module for requirement no. 43 to automatically change to the same value. This does not have to happen in real time, more realistically I'm picturing a scenario where you every now and then run your script to update the source module. Is this possible? And if so, can you suggest some basic guidelines? PS: I'm assuming DXL is the best way to solve this problem, but if anyone know of an already built in function that achieves this, please let me know :) kip820 - Thu Jun 27 09:04:49 EDT 2013 |
Re: How to update attributes connected by links I would use a traceability column showing the value of Status attribute in the Proof module. Is this for some reason not working for you? |
Re: How to update attributes connected by links Pekka_Makinen - Thu Jun 27 09:13:34 EDT 2013 I would use a traceability column showing the value of Status attribute in the Proof module. Is this for some reason not working for you? You Sir are a genius, or I am very stupid, or possibly both ;) |
Re: How to update attributes connected by links Pekka is right, you want to display here a value found in the linked object. In this case it appears you want the requirement to display "Proven" or "Whaterver" based on the value in the linked proof object. Since I HATE layouts with a passion, I would be tempted to get the traceability to work, and then convert it to an attr DXL. That reduces thrashing but more importantly it lets you query the "status" via DXL of the requirement object.
Otherwise you need to write the code to follow the lnk and do the query there. On another topic ... I think it well advised that your Proof module source the links TO your Requirement module; presumably you write your requirements first and then prove them and you may want to lock your requirements down. -Louie |